Method and systems for short message forwarding services

ABSTRACT

Methods and systems are described for processing visual messages, such as text or multimedia messages, originated from a mobile phone. In an embodiment, a visual message from an originating wireless telephonic device is directed to an original destination address associated with a user. An indication that the visual message has been received at a first telecommunications system, wherein an original destination associated with the original destination address is not available to receive the originating wireless telephonic device visual message. The visual message is wirelessly transmitted to an alternate destination.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority from U.S. Patent Application No.60/811,068, filed Jun. 5, 2006, the content of which is incorporatedherein in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED R&D

Not applicable.

PARTIES OF JOINT RESEARCH AGREEMENT

Not applicable.

REFERENCE TO SEQUENCE LISTING, TABLE, OR COMPUTER PROGRAM LISTING

Not applicable.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to telecommunications andmessaging and in particular, to systems and methods for handlingmessages over a wireless network.

2. Description of the Related Art

In conventional wireless networks, users generally have the ability tosend and receive text messages between other wireless users or otherhand held devices. This service is referred to as a Short MessagingService.

For example, conventionally messages are sent from a mobile user via astore-and-forward mechanism to a Short Message Service Center (SMSC),which will attempt to send the message to the recipient and possiblyretry sending the message if the user mobile device is not reachable ata given moment. However, conventionally, message delivery is on a bestefforts basis. Thus, message delivery to a designated recipient is notguaranteed, and delay or complete loss of a message is not uncommon,particularly when sending SMS messages between network operators.

SUMMARY OF THE INVENTION

Example methods and systems are described that can be utilized towirelessly forward a message (e.g., an SMS or MMS message) to adestination, such as a destination other than the originally addresseddestination. For example, a forward operation may be triggered when acertain condition is detected, such as when the original destination(e.g., a mobile phone), is not available to receive the message. Certainembodiments further forward or broadcast a message (e.g., an SMS or MMSmessage) to a plurality of destinations, even if the message isaddressed to a single destination. Certain embodiments store a messageintended for an unavailable destination, such as a mobile phone, andwhen the destination becomes available, transmits the stored message tothe destination.

An example embodiment provides a method of communicating a ShortMessaging Service message from an originating device directed to anoriginal destination address associated with a user, the methodcomprising: receiving at an SMS relay an indication that an SMS messagehas been received, the indication including the original destinationaddress, wherein an original destination associated with the originaldestination address is not available to receive the SMS message; storingthe SMS message on a networked server; and transmitting to atelecommunications client and/or an email address associated with theuser an indication that an SMS message has been received.

An example embodiment provides a method of communicating a mobile phonemessage from an originating wireless mobile telephonic device directedto an original destination address associated with a user, wherein themobile telephonic device message is a text message or multimediamessage, the method comprising: receiving at a first telecommunicationssystem an indication that a mobile telephonic device message has beenreceived, the message including the original destination address,wherein an original destination associated with the original destinationaddress is not available to receive the mobile telephonic devicemessage; and transmitting to a telecommunications client and/or an emailaddress associated with the user an indication that a mobile telephonicdevice message has been received.

An example embodiment provides a method of communicating a visualmessage from an originating device directed to an original destinationphone address associated with a user, the method comprising: receivingat a first telecommunications system an indication that the visualmessage has been received, wherein an original destination associatedwith the original destination phone address is not available to receivethe originating visual message; and transmitting the visual message toan alternate destination specified by the user.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described withreference to the drawings summarized below. These drawings and theassociated description are provided to illustrate example embodiments ofthe invention, and not to limit the scope of the invention.

FIG. 1 illustrates an example network operating environment for advancedtelecommunications services.

FIG. 2 illustrates a first example operating environment and examplemessaging service.

FIG. 3 illustrates a first example telecommunications client call logand user contacts user interface with text reply and forward.

FIG. 4 illustrates an example user interface of a call log via a webbrowser.

FIG. 5 illustrates an example user interface of a text message creationwindow.

FIG. 6 illustrates an example user interface for configuring ShortMessage Forwarding service using a web browser.

FIGS. 7A-B illustrate still another example user interface.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments herein relate to telecommunications and messaging, and, forexample, to methods and systems for providing messaging services, suchas Short Message forwarding services or Multimedia Message forwardingservices.

By way of example, methods and systems are described that wirelesslyforward a message (e.g., an SMS or MMS message) to a destination otherthan the addressed destination and/or that forward or broadcast amessage (e.g., an SMS or MMS message) to a plurality of destinations,even if the message is addressed to a single destination.

In an example embodiment, a Short Message Forwarding service (or othervisual message forwarding service that handles messages intended to beviewed or read) provides additional value to wireless network customersor to other customers that communicate using SMS (or other visualmessage service) by enabling them to receive a forwarded Short Message(or other visual message) at another destination or device when theoriginally messaged destination (e.g., a mobile cellular phone, personaldigital assistant, other SMS-capable mobile device, or other SMS device)is not accessible, e.g., is off or is out of range. Optionally, usingmessage forwarding, the Short Message may still be delivered to theoriginally messaged destination when it is again accessible. Because themessage is forwarded, the message may reach the destination device andthe designated recipient in a more timely fashion.

Certain example methods and systems described herein enable a user toreceive a message (e.g., a Short Message Service text message, aMultimedia Message Service multimedia message, etc.) at a location otherthe original designated destination (e.g., at a location other than auser's mobile device to which a Short Message Service text message isaddressed), optionally while also receiving the message at the originaldesignated location. In contrast to many conventional user interfaces,certain embodiments of the Short Message-related processes and apparatusdisclosed herein take advantage of a telecommunications client hosted ona user terminal and connected to the telephone network (e.g., the publicswitched telephone network (PSTN), a wireless network, etc.) over theInternet.

In an example embodiment, the customer may configure one or more SMS/MMSand email forwarding addresses. Optionally, a message is sent to eachaddress when a Short Message or Multimedia Message is received by anSMSC or a softswitch, as described below.

For example, optionally, a Short Message (SM) and/or email willautomatically be forwarded to a telecommunications client as a default,but the subscriber can specify (e.g., via an account set-up/members zoneWeb page, via a Web site of a corresponding carrier partner, or via atelecommunications client, wherein the specification is stored incomputer readable memory such as a database) that the SM be forwarded toother destinations instead of or in addition to the client. Optionally,an SM will not be forwarded to the telecommunications client unless thesubscriber so specifies in the subscriber's account setup.

In an example embodiment, an underlying wireless carrier providing theShort Message Service and/or a Multimedia Message Service is equippedwith a database, such as a Home Location Register (HLR), that containsinformation (e.g., a mobile device identifier, a mobile device telephonenumber, call/message forwarding information, location updates, and/or anindication as to whether the mobile device is roaming, with a mobiledevice is registered, etc.) regarding wireless subscribers and theirmobile device(s), and a system for storing a message and transmittingthat message to its destination, such as a Short Message Service Center(SMSC) and/or a Multimedia Service Center (MMSC), configured andenhanced to support Short Message Forwarding and Multimedia MessageForwarding as described herein.

Throughout the following description, the term “Web site” or “Web” isused to refer to a user-accessible network site that implements thebasic World Wide Web standards for the coding and transmission ofhypertextual documents. These standards currently include HTML (theHypertext Markup Language) and HTTP (the Hypertext Transfer Protocol).It should be understood that the term “site” is not intended to imply asingle geographic location, as a Web or other network site can, forexample, include multiple geographically distributed computer systemsthat are appropriately linked together. Furthermore, while the followingdescription relates to an embodiment utilizing the Internet and relatedprotocols, other networks, such as networked interactive televisions,and other protocols may be used as well.

In addition, throughout the following description, the terms message,messaging, and Short Message are used to refer to text messages as wellas to mixed media messages including but not limited to text or othervisual messages (e.g., including Instant Messages), MMS, voice, fax,HTML, photos, video, music, program code, etc. Message content can beembedded in the body of the message, included as an attachment (e.g., atext file or voice attachment), or referenced or linked (e.g., by use ofan embedded URL).

Further, while the following description refers to example network,messaging (e.g., SMS), and telephony standards and protocols (e.g., SS7,wireless protocols, etc.), other standards and protocols can be used aswell. In addition, while references may be made to electronic addressbooks or contact lists, other data stores and formats can be used tostore contact information. In addition, unless otherwise indicated, thefunctions described herein may be performed by executable program codeand instructions stored in computer readable memory and running on oneor more processor-based systems. However, state machines, and/orhardwired electronic circuits can also be utilized. Further, withrespect to the example processes described herein, not all the processstates need to be reached, nor do the states have to be performed in theillustrated order. Further, certain process states that are illustratedas being serially performed can be performed in parallel.

Similarly, while certain examples may refer to a personal computersystem or data device, other computer or electronic systems can be usedas well, such as, without limitation, an interactive television, anetworked-enabled personal digital assistant (PDA), a networked gameconsole, a networked entertainment device, and so on. While certainreferences are made to certain example system components or services,other components and services can be used as well. In addition, whilecertain user inputs are described as being provided via phone keypresses or by clicking on a button, optionally, user inputs can beprovides using other techniques, such as by voice or otherwise. Whilecertain phone numbers are referenced for purposes of illustration, otherphone numbers or electronic addresses or locators can be used as well.

The term phone address can include a SIP address, a Skype address (orother peer-to-peer Internet telephony network address), a wireless phonenumber, an International number, an E.164 phone number, or otheraddress. While Skype is referred to herein, other peer-to-peer telephonynetworks (e.g., having a decentralized and distributed user directorydistributed among the nodes in the peer-to-peer telephony network) maybe used as well to receive calls, place calls, and/or transfer calls.While certain phone addresses are referenced for purposes ofillustration, other electronic addresses or locators can be used aswell. While a SIP federated phone may be referred to, other data phones,such as an XMPP federation phone, a Skype phone (or other phone thatcommunicates via a peer-to-peer telephony network), or other networkedphone, which may be in the form of a softphone, may be used.

The term mobile device can include a telephone, such as a cellularmobile device compatible with CDMA, GSM, HSDPA, UMB, WiMax, and/or otherstandards

In addition, certain call management capabilities described herein makeuse of a telecommunications client (e.g., a personal computer client, aclient hosted on an interactive television, a network personal digitalassistant, a smart phone, or a wireless phone with an Internetconnection, etc.) to give the customer access to and management of calls(e.g., see example user interface illustrated in FIG. 3). Optionally, acustomer can have multiple clients hosted on multiple computers or otherhosts.

In an example embodiment, the telecommunications client applicationconnects to and communicates with a system (e.g., a softswitch) via theInternet, an intranet, and/or other network. The client application,executing on a subscriber's computer terminal or other host, can makethe subscriber's online presence known to the softswitch (e.g., bytransmitting a message over the Internet to the softswitch). The clientcan be used to receive, edit, and display call log data from thesoftswitch (e.g., a list of calls placed to/received by the subscriber,or placed by the subscriber, including phone numbers, caller or calledparty names, date/time of the call, an indication as to whether a callwas an outbound/inbound call, the city/state of the caller/called party,type of call voice, text, or fax, etc.), and call alert data (e.g., foran active call, listing the caller phone number, name, city/state,and/or call status (e.g., ringing, playing greeting, recording callermessage, terminating call, displaying fax)). Optionally, the call alertalso plays an audible signal, such as a ring tone.

The client application can display a log of recorded or receivedmessages from callers, and can provide playback controls (e.g., play,fast forward, rewind) for playing back or displaying the recordedmessage (e.g., a voice message, a video message, a fax message, a textmessage, etc.) via the client computer terminal. The client optionallycan also be used to screen calls (e.g., wherein the softswitch streams amessage being left by a caller and stored in memory to the client sothat the called party can listen to the message in substantially realtime) and to instruct the softswitch to accept calls on the hostcomputer terminal, forward calls, refuse calls, initiate callconferencing, and to otherwise provide call handling instructions.Optionally, the client application can be automatically and/or manually(e.g., directly in response to a user instruction) upgraded to a neweror different version over a data network, such as the Internet. Forexample, a system, such as an upgrade manager system (e.g., as part ofthe call processing system or independent of the call processingsystem), can provide client application downloads to users based on thecurrent version being used by the users (e.g., are they using versionsolder than an available upgrade) and/or a level of authorizationassociated with users (e.g., is the user entitled to an upgrade). Theupgrade manager system can download the application to the applicationhost terminal in burst mode and/or in a trickle, background mode.

The telecommunications client is an example user interface and otheruser interfaces can be used in addition or instead. FIG. 4 illustratesanother example call log user interface presented via a browser to acustomer. The browser can be executing on a computer terminal, such as apersonal computer, a smart phone, a browser/Wireless ApplicationProtocol (WAP)-enabled phone, a PDA, or the like. The call log can beaccessed by supplying the appropriate URL to the browser and optionallyproviding log-on information, such as a user name and a password.

Enhanced service providers, such as CallWave, have emerged, providingnew features and functions on ordinary phone calls. By way of example,CallWave provides call screening and transfer features that enhance thecustomer's calling experience, such as those described in U.S. Pat. No.7,103,167, the contents of which are incorporated herein in theirentirety by reference. Other embodiments of Short Message serviceapplications are described in U.S. Pat. No. 6,879,677 issued Apr. 12,2005, the contents of which are incorporated herein in their entirety byreference.

Other embodiments of related call management functions—call logging,caller name, call screening, fixed-mobile converged routing, privacymanagement, and bridged outcall—some or all of which can be applied inoffering this service, are described in the following patentapplications, the contents of which are incorporated by reference intheir entirety:

-   U.S. patent application Ser. No. 11/366,989, filed Mar. 2, 2006,    entitled “Methods and Systems for Creating a Dynamic Call Log and    Contact Records”;-   U.S. patent application Ser. No. 11/685,678, filed Mar. 13, 2006,    entitled “Methods and Systems for Personalizing Calling/Caller    Name”;-   U.S. patent application Ser. No. 11/374,390, filed Mar. 13, 2006,    entitled “Systems and Methods for Call Screening”;-   U.S. patent application Ser. No. 11/040,185, filed Jan. 21, 2005    entitled “Methods and Systems for Transferring Data Over a Network”,-   U.S. Provisional patent application Ser. No. 11/676,933, filed Feb.    20, 2007, entitled “Methods and Systems for Providing Call Screening    Using Network Triggers”.

The functionality, operation, and implementation for an example ShortMessage Forwarding service will now be described in detail.

GLOSSARY

AIN—Advanced Intelligent Network

CP—Carrier Partner

IP—Intelligent Peripheral

MSC—Mobile Switching Center

MVNO—Mobile Virtual Network Operator

SCP—Service Control Point

SM—Short Message

SMS—Short Message Service

SMSC—Short Message Service Center

SMPP—Short Message Peer to Peer Protocol

SS7—Signaling System 7

SSP—Service Switching Point

TCAP—Transaction Capabilities Application Part

FIG. 1 illustrates an example advanced telecommunications networkenvironment.

A carrier (e.g., a Carrier Partner who is a partner or has anarrangement with a third party call processing operator in providingenhanced call processing services) customer has one or more landlinephones that connect to an SSP 104 (Service Switching Point) in thecarrier's network 106. The user/customer may also have one or moremobile phones 134 and one or more hosts (e.g., personal computers, smartphones, interactive televisions, networked game consoles, etc.)executing a telecommunications client 136. The telecommunications client136 has one or more user interfaces that optionally display some or allof the following: a call log (including a log of SMS or other visualmessage), a contact record/list, and active, in-progress calls, andspeed dial assignments.

Optionally, the customer can elect to screen or take an active call viathe client 136 (e.g., where the customer hears the caller recording amessage by the softswitch via a half-duplex streaming of the message tothe client 136, but where the caller cannot hear the customer).Optionally, calls can also be made via the telecommunications client 136(e.g., where the host is equipped with a speaker and microphone).Optionally, the telecommunications client 136 also displays textmessages, such as SMS or instant messages.

Some or all of the foregoing client capabilities can optionally beprovided via one or more web pages, widgets, gadgets, or other userinterfaces. Further, optionally a subscriber can configure certainaspects of their account, such as forwarding rules (e.g., SMS, MMS,and/or other message forwarding rules), speed dial assignments, ringbacksignal assignments, busy signal assignments, call routing prioritiesand/or other instructions, via the telecommunications client 136, anaccount configuration/set-up web page (e.g., hosted by the softswitch114), a widget, a gadget, or otherwise.

In this example, the softswitch 114 has one or more components, some ofwhich are optionally centralized at a given location, others of whichmay be co-located in the carrier's network (e.g., to reduce networktransport costs). The SCP 116 (Service Control Point) is an AINcomponent that interacts with one or more SSPs 104 (e.g., using the TCAPprotocol). AN triggers are optionally armed for the customer's landlinephone number/address/account so that when calls are made to or from thelandline phone 132 (e.g., a POTS landline phone that communicates via aswitched circuit network such as the PSTN 108), a trigger fires andcauses the SSP 104 to query the SCP 116 for instructions on how tohandle the call. The SCP 116 is optionally also configured to performTCAP queries to other SS7 components as needed by some services (e.g.,request Automatic Callback from another carrier's switch when a linebecomes idle) or to provision certain features.

Optionally, SS7 Wireless Intelligent Network (WIN) triggers and featuresare set in the mobile switches of Wireless Carrier Partners to providesimilar calling services but for a customer's mobile phonenumber/address/account.

The softswitch 114 also optionally contains one or more systems 126,referred to herein as call managers. The call managers 126 are connectedto the PSTN 108 (e.g., via ISDN using the ISUP (ISDN User Part)protocol, by way of example). The call managers 126 service or providesome or all of the following: provide a call screening service whenscreening is to be provided, record a message from a caller that is tobe recorded, provide a voice prompt or message that is to be played to acaller and/or called party, record a facsimile document that needs to berecorded in a database, detect speech or DTMF tones, convert speech thatneeds to be converted to text, and/or provide an inbound/outboundgateway between the SS7 network and SIP networks. The example callmanager 126 optionally can also act as an IP (Intelligent Peripheral),another AIN component that the SCP 116 can instruct the SSP 104 toconnect into the call for interaction with the called and calling party.The IP/call managers 126 and SCPs 116 in the softswitch 114 optionallyshare a Call Registry that stores information about active calls.

The session managers 126 in the softswitch 114 track telecommunicationclient 136 presence and interact with a given telecommunications client136 (e.g., a personal computer client) as call log, contact, and/orcustomer data need to be synchronized with centralized databases toprovide the customer, via the client 136, with updated log, contact,and/or customer data. The session managers 126 also optionally providethe SCP 116 with service configuration information for the customerinvolved in a call. During an active call, the SCP 116 and/or IP/callmanager 126 optionally directly interact with the telecommunicationsclient 136 to provide call progress information, and to stream audio tothe client 126.

The softswitch 114 in this example contains centralized databases and/orgeneral-purpose storage areas, optionally including, but not limited to,some or all of the following: a call log database 118, a contactsdatabase 120, and a customer database 122. The call log database 118stores call events and related data for incoming and outgoing calls. Thecontacts database 120 stores information and parameters (e.g., names,identifiers, and/or phone numbers/addresses, etc.) associated with acalled or calling party. The customer database 122 stores informationand parameters (e.g., account data and configuration information)associated with subscribers/customers.

The softswitch call processing system 114 optionally includes one ormore other subsystems, such as some or all of the following: a routersubsystem, which serves as an interface to the Internet to managecommunications between online IP client devices and one or more callprocessing servers, a web server subsystem to manage a “website”associated with the softswitch 114 (e.g., via which a user can access anaccount set-up/configuration user interface, a speed dial assignmentuser interface, a call log 118, a contacts database 120, etc., using abrowser or other network user interface), etc. These foregoingsubsystems are optionally interconnected via a Local Area Network (LAN),a Wide Area Private Network (WAN), and/or a Wide Area Public Network(e.g., Internet).

The call manager 126 can communicate with the mobile phones 134 acrossthe PSTN 108 over a wireless network 112 via the corresponding MSC 110.The softswitch 114 (e.g., via the call manager 126 and session manager124) can communicate over the Internet 128 with the telecommunicationsclient 136, browsers, widgets, etc.

As illustrated in FIG. 2, the softswitch 114 call processing systemoptionally includes one or more other subsystems, such as some or all ofthe following: an SMS relay 204 subsystem, which receives inbound ShortMessage Service messages (also referred to herein as Short Messages) viaan SMPP protocol for example; an email relay subsystem 208 which formatsand sends email messages via SMTP, by way of example; a routersubsystem, which serves as an interface to the Internet to managecommunications between online IP client devices and one or more callprocessing servers, a web server subsystem to manage a websiteassociated with the softswitch 114 (e.g., via which a user can access anaccount set-up/configuration user interface, a call log, a contactsdatabase, etc., using a browser or other network user interface), etc.These foregoing subsystems are optionally interconnected via a LocalArea Network (LAN), a Wide Area Private Network (WAN), and/or a WideArea Public Network (e.g., Internet).

FIG. 2 depicts an example scenario in which a person uses their mobilephone to send a message, such as a Short Message (SM), to a designatedrecipient's mobile phone (although a different type of SMS-enable devicecan be a destination). However, designated recipient's mobile phone isunavailable (e.g., the designated recipient turned off the destinationmobile phone upon coming home), and thus cannot receive the message. TheSM is then forwarded to the designated recipient's telecommunicationsclient (e.g., hosted on the designated recipient's personal computer orother host) per forwarding rules configured by the service provider oruser (e.g., via an account set-up/members zone Web page, via a Web siteof a corresponding carrier partner, or via a telecommunications client,wherein the rules or configuration is stored in a database, such as acustomer account database) in the wireless network. In this example, theuser specified that a notification regarding SMS messages (optionallyincluding the message, sender name, and time of transmission and/orreceipt) is to be transmitted to a specified email address. The exampleSM handling sequence scenario of FIG. 2 is now described in more detail:

State 1. The Sender, using mobile phone 202 (or other device capable ofsending a Short Message), composes an SM and addresses it to theDesignated recipient's mobile phone 134 (or other device capable ofreceiving Short Messages). The mobile phone 202 wirelessly transmits theSM. A Mobile Switching Center (MSC 214, which may be the same as MSC 110illustrated in FIG. 1) (or other telephone exchange which providescircuit-switched calling, mobility management, communication services tomobile phones roaming within the area served by the exchange, such asvoice, data, SMS, and/or call forwarding services), currently servingthe Sender receives the SM.

State 2. The MSC 214 sends the SM to the home Short Message ServiceCenter (SMSC 208).

State 3. The SMSC 208 queries the Home Location Register (HLR 210) forthe location of the phone to which the SM is addressed. The HLR 210, inthis example, indicates that the Designated recipient's mobile phone isnot currently registered in the wireless provider's network and returnsto the SMSC 208 the configured SM forwarding address.

State 4. In this example, the forwarding address is not one served bythe SMSC 208, so the SMSC 208 makes a copy of the message, addresses itto the HLR 210 specified forwarding address, and sends it to theInter-Carrier SMS gateway 212 used by the that wireless carrier. TheSMSC 208 also queues the SM for later wireless delivery to theDesignated recipient's mobile phone 134.

State 5. The Inter-Carrier SMS gateway 212 recognizes the address in thereceived SM as being serviced by another carrier. The Inter-Carrier SMSgateway 212 creates a connection to the SMS relay 204 in the softswitch114 of the carrier serving the Designated recipient and using a messagetransport protocol (e.g., Short Message Peer to Peer (SMPP) protocol)transfers the SM the SMS relay 204.

State 6. The SMS relay 204 within the softswitch 114 sends anotification message to the session manager 124 indicating that an SMhas been received. The notification message includes the originaldestination address or other identifier associated therewith.

State 7. The session manager 124 verifies the address or otheridentifier is that of a customer (e.g., a subscriber of a serviceoffered by the operator of the softswitch 114 and/or other entity havingan account associated with the softswitch 114), optionally bydetermining if the address or other identifier matches or corresponds toa customer address or other identifier in the customer database 122(which stores customer account records). The session manager 124optionally notifies one or more telecommunication clients that arecurrently online (e.g., such as client 136) via a wired and/or wirelessnetwork associated with the customer of the new message. In thisexample, since the designated recipient also configured the service(e.g., via a web interface) to be notified of messages at a specifiedemail address, the session manager 124 returns this email address to theSMS relay 204.

State 8. The SMS relay 204 transmits the SM message to the email relay206 to send the SM to the Designated recipient's specified email addressvia a wired or wireless network. The SM text, other media and otherattachment or link, if any, are included in the message.

State 9. In response to the session manger notification, thetelecommunications client 136 alerts the designated recipient that a newmessage has been received via visual and/or audible notifications viathe telecommunications client or browser user interface. The Designatedrecipient clicks on the message notification entry to have the clientapplication 136 or browser user interface display the message(optionally the client can be configured to automatically display themessage), reviews the message, and composes and sends a reply (e.g.,using the example interface illustrated in FIG. 5). The reply followsthe reverse path through the session manager 124, SMS Server, SMSgateway 212, SMSC 208, and MSC 214 back to the mobile phone 202 (orother sending device) of the original Sender. The Designated recipient'smobile phone address is optionally automatically used as the “from”address for the reply.

State 10. When the Designated recipient's mobile phone 134 is nextturned on (e.g., the next morning), the mobile phone registers with thenearest MSC (e.g., MSC 214) if one is available.

State 11. The MSC 214 informs the HLR 210 of the registration (e.g., viaa message transmitted from the MSC 214 to the HLR 210).

State 12. The HLR 210 informs the SMSC 208 via a message transmittedfrom the HLR 210 to the SMSC 208 of the registration since it knowsthere is an SM queued.

State 13. The SMSC 208 transmits the queued SM to the MSC 214.

State 14. The MSC 214 transmits a notification to the mobile phone 134informing the mobile phone there is a message waiting. In response, themobile phone display displays an icon and/or text indicating that thereis an SM waiting.

State 15. The Designated recipient notices the message waiting iconand/or text via the mobile phone 134 and requests to view the SM (e.g.,via a menu selection, by clicking on an entry corresponding to the SM,or otherwise). The Designated recipient deletes the message as it is anold message that was previously reviewed (e.g., via thetelecommunications client or browser at state 9).

At state 4 above, optionally rather than sending the message to anInter-Carrier Gateway, the SMSC 208 is configured to send a copy of themessage directly to: a) a subscriber's forwarding address, b) to amessage relay (e.g., in the softswitch 114), and/or c) one or morecomputer telecommunications clients over an IP connection. Otherforwarding service implementations can be used as well.

At state 4 above, the HLR query by the SMSC 208 can be configured togenerally or always return a forwarding address. Optionally, any ShortMessage directed to a designated recipient (or Short Message meetingcertain criteria, such as being on a forwarding list or not being on ado not forward list) is mirrored to one or more telecommunicationclients associated with the designated recipient and one or more emailaddresses, instant messaging addresses, or other addresses. Optionally,a message sync function is provided whereby deleting a message on onemessage store (e.g., a telecommunication client host), triggers orcauses the deletion of queued messages at the SMSC 208.

The HLR 210 stores a forwarding address or equivalent identifier,similar to how the HLR 210 stores a call divert setting or forwardingphone number for missed calls. This forwarding address is optionallyconfigured via the Web interface (e.g., via an account set-up/memberszone Web page, via a Web site of a corresponding carrier partner, or viaa telecommunications client), which in turn interfaces to the HLR 210 toperform the configuration edit. In addition or instead, the forwardingaddress is optionally configured by the user sending an SM to a specificdesignated phone number or destination. Other methods of configuring aforwarding address within the HLR 210 include but are not limited tohaving the service provider's call center or an Interactive VoiceResponse system.

The SMSC 208 is optionally also configured to receive and apply aforwarding address from the HLR 210 when the recipient of an SM is notregistered for service with the HLR 210.

Optionally, in addition or instead, the SMS relay 204 is configured tonotify the SMSC 208 if the SMS relay 204 has positive acknowledgementthat the customer viewed the SM at the telecommunications client 136,and could therefore remove the message from the SMSC queue.

When a user (e.g., a customer that subscribes to or otherwise has theShort Message Forwarding service) modifies a forwarding address (e.g.,via an account set-up/members zone Web page, via a Web site of acorresponding carrier partner, via a telecommunications client, orotherwise), the softswitch interfaces with the carrier partner's HLR (orentity storing the forwarding address parameter) to make the change. Theinterface with the Carrier Partner's HLR can be performed substantiallyimmediately after the user specifies or modifies the forwarding address,at a scheduled time, or otherwise. An example forwarding address is inthe form <phoneNumber>@domainname.tld (top level domain, such as .com,.net, .org, .edu, .gov, or other TLD) (e.g., 8055554100@callwave.com).The Inter-Carrier SMS Gateway or SMSC is preconfigured to routeaddresses of this format, and this domain in particular, to thecarrier's softswitch that performs a message routing function. Thisinterface offers the option of forwarding Short Messages to theforwarding address, regardless of whether the mobile phone itself iscurrently available to receive the message.

FIG. 6 depicts an example web page used to configure the Short Messageforwarding service address. A user can specify that Short Messageforwarding is to be enabled or disabled via one or more correspondingfields or controls. The user can also enter into corresponding fieldsone or more forwarding addresses (e.g., forwarding email addresses).Other methods can be used to configure the Short Message forwardingservice address, such as interactive voice response system or callcenter, by way of example and not limitation.

FIG. 3 illustrates another example user interface that displays a calllog, wherein a call log entry optionally includes the date and time acall was received and if the caller's phone address is not private, thesource of the call (e.g., an icon indicating whether the call was placedfrom the user's home, work, mobile, or fax phone address), the caller'sphone address and/or name or other identifier. An entry can alsoindicate whether there is a recorded message left by the caller, andoptionally the length (e.g., in seconds) of the message. Similarly, anentry can indicate whether a call is a fax call, and the length of thefax received (e.g., in pages).

A message, such as an SMS Short Message or an MMS message is optionallytreated as another type of call or message by the telecommunicationsclient. As illustrated in FIG. 3, the SM is optionally listed in thecall log pane with other calls and messages. A Short Message log entryis optionally distinguished by an icon, coloring, and/or a label (e.g.,SMS') in the details column of the log. The sender name (or otheridentifier), message length (e.g., in characters), and date/time themessage was received can also be displayed.

New entries that have not yet been reviewed are optionally highlighted.A “new call” area displays the number of new calls the user hasreceived. A contacts area displays at least a portion of a contactrecord for a contact (e.g., a contact corresponding to a selected logentry or otherwise selected).

By way of example, the contact record can include some or all of thefollowing: contact name, address, phone address(es), email address(es),SMS address, company, title, name of ringback signal assigned to thecontact, notes, and other information. An edit control is provided,which when activated, causes the contact record to be editable, whereinthe edited contact record can then be saved into the contact databasediscussed herein. A “new” control is provided for creating a new contactrecord. A “click to add name” control is provided which, when activated,provides a user interface via which the user can add a name to a contactrecord that contains contact information, but not a contact name.Optionally, this user interface can display a speed dial assignment, assimilarly discussed above.

When a Short Message entry in the log is selected, clicking on theplay/view icon or double clicking on the selection optionally causes theShort Message to be displayed in the top pane of the telecommunicationsclient.

Optionally, Delete, Reply, and Forward buttons or other controls areprovided and displayed for responding to received Short Messages.Optionally, Reply and Forward requests result in a window being openedsuch as the example user interface illustrated in FIG. 5. Via the userinterface, the user can enter into corresponding fields the name of arecipient (e.g., via a “to” field), an address, a subject, and amessage. The user can also specify that a voice message is to beattached to the SM message. The user can record the voice message usinga telecommunication client host microphone. Optionally, the userinterface displays the current date. Optionally, a browse control isprovided, which, when activated, enables the user to browse to or searchfor a desired file or link to attach or embed. Once the user locates thedesired file or files, the user can select the file(s) or links thereto,which are then embedded or attached to the message. Optionally, a fieldis provided wherein the user can manually enter a desired file nameand/or path. The user can optionally specify whether the file is to beembedded, attached, or linked. By way of example and not limitation, thefiles can include one or more of voice, fax, HTML, photos, video, music,program code, links, etc.

FIG. 7A illustrates an example widget user interface displaying callinformation for the most recent received call. The user interfaceincludes some or all of the following: the name/identifier (ifavailable) of the caller/sender, the date of the call/message, the timeof the call/message, the connect time for the call, length of messageleft (if any), or length of fax received (if any). In the illustratedexample, the user interface indicates that an SMS message including 47characters was received. An expand control is provided to expand thesize and/or amount of information displayed. An account control isprovided, which when activated causes an account management Web page tobe presented. A feedback control is provided which, when activated,causes a form to be presented via which the user can submit feedback tothe system operator/provider (e.g., like and dislikes regarding thesystem and services, problem issues, etc.), access a help interface,and/or access answers to frequently asked questions. A “see all calls”control is provided, which when activated, causes the user interface tolist numerous past calls (e.g., all past calls, all past call receivedin a certain time period whose entries have not been deleted, a certainnumber of past calls, etc.), optionally in a scrollable user interface.

FIG. 7B illustrates an example expanded version of the user interfaceillustrated in FIG. 7A. The example view displays for an SMS message thecalling number/SMS address and the message text (optionally in ascrollable window/area).

The Short Message Forwarding service can operate in the followingexample carrier environments wherein the carrier (e.g., the CarrierPartner):

Identifies which customers are to have the Short Message Forwardingservice enabled and for each identify their mobile phone number.

Utilizes a wireless network where the HLR and SMSC support forwarding.

Enables a message routing capable softswitch to interface with the HLRand SMSC to configure forwarding addresses and to indicate whether toforward all Short Messages or only those received when the given mobilephone is not available to receive the message.

Configures the Inter-Carrier SMS Gateway or SMSC to route all ShortMessages with addresses of the form <phoneNumber>@domainname.TLD to theforwarding address or to a softswitch that can route the messages totheir destination addresses.

Thus, example methods and systems are described that can be utilizedwirelessly forward a message (e.g., an SMS or MMS message) to adestination other than the addressed destination (e.g., when theaddressed destination, such as a mobile phone, is not available) and toforward or broadcast a message (e.g., an SMS or MMS message) to aplurality of destinations, even if the message is addressed to a singledestination. Certain example embodiments described store a messageintended for an unavailable destination, such as a mobile phone, andwhen the destination becomes available, transmits the stored message tothe destination.

It should be understood that certain variations and modifications ofthis invention would suggest themselves to one of ordinary skill in theart. The scope of the present invention is not to be limited by theillustrations or the foregoing descriptions thereof.

What is claimed is:
 1. A method of managing Short Messaging Servicemessages, the method comprising: receiving at an SMS relay first SMSmessage; providing a copy of the first SMS message to atelecommunications client associated with the user; and storing thefirst SMS message on a networked server accessible over a network by theuser via the telecommunication client, wherein the telecommunicationsclient includes a user interface via which the user can view the storedfirst SMS message from the networked server and (a) delete the first SMSmessage from the networked server, or (b) forward the first SMS messagestored on the networked server, or (c) reply to the first SMS messagestored on the networked server, or (d) edit an originating phone numberassociated with the first SMS message stored on the networked server, or(e) create a contact from the first SMS message stored on the networkedserver, or (f) originate a call to the originating mobile device via thefirst SMS message stored on the networked server, or any combination of(a), (b), (c), (d), (e) and (f); receiving at the SMS relay a second SMSmessage including a corresponding destination address associated with adevice of an intended recipient; querying a Home Location Register (HLR)regarding a status of a device associated with the destination addressof the intended recipient; receiving an indication from the HLR as towhether the device of the intended recipient of the second SMS messageis available; at least partly in response to an indication from the HLRthat the device of the intended recipient is not available to receivethe second SMS message, causing at least in part an email to betransmitted to a forwarding email address associated with the intendedrecipient, wherein the forwarding email address is received from theHLR, the email including content of the second SMS message, a link tothe second SMS message's content, or the second SMS message's contentand the link to the message content of the second SMS message.
 2. Themethod as defined in claim 1, wherein the telecommunications client ishosted on a device other than the user's mobile phone.
 3. The method asdefined in claim 1, wherein the telecommunications client is accessiblevia an interactive television.
 4. The method as defined in claim 1,wherein the originating device includes a personal computing device andthe telecommunications client is downloaded to the personal computingdevice, the telecommunications client being capable of transmitting SMSmessages.
 5. The method as defined in claim 1, wherein thetelecommunication client is configured to be upgraded over a datanetwork.
 6. The method as defined in claim 1, the method furthercomprising receiving a reply message from the user via thetelecommunications client, and at least partly causing the reply messageto be transmitted to the originating mobile device that originated theSMS message.
 7. The method as defined in claim 6, wherein the replymessage is communicated via an SMS gateway and a mobile switching centerto the mobile phone.
 8. The method as defined in claim 1, wherein theSMS message is stored in a queue and the queued SMS message istransmitted to the original destination when the original destinationbecomes available.
 9. The method as defined in claim 1, wherein the SMSmessage is stored in a queue to be delivered at a later time to theoriginal destination, and at least partly in response to a deletioninstruction being provided via the telecommunications client, causingthe SMS message to be removed from the queue so that the SMS message isnot transmitted to the original destination.
 10. The method as definedin claim 1, the method further comprising providing a user interface viawhich the user can provide an SMS message forwarding address.
 11. Themethod as defined in claim 10, wherein the SMS forwarding address is anemail address.
 12. The method as defined in claim 1, wherein thetelecommunications client is hosted by a personal computer or aninteractive television.
 13. The method as defined in claim 1, whereinthe telecommunications client includes a widget.
 14. The method asdefined in claim 1, the method further comprising providing a call loguser interface via the telecommunications client hosted on a desktoppersonal computer, the call log including the SMS message and anidentifier associated with a sender of the SMS message.
 15. The methodas defined in claim 1, wherein the telecommunications client is hostedat least on a device other than user mobile device, and wherein the usercan delete the stored SMS message via the telecommunication client. 16.The method as defined in claim 1, wherein the telecommunications clientis hosted at least on a device other than user mobile device and isconfigured to be upgraded over a data network, and wherein, via thetelecommunications client, the user can: delete the SMS message from thenetworked server, and forward the SMS message stored on the networkedserver, and reply to the SMS message stored on the networked server, andcreate a contact from the SMS message stored on the networked server,and originate a call to the originating mobile device via the SMSmessage stored on the networked server.
 17. The method as defined inclaim 1, wherein SMS will not be forwarded to the telecommunicationsclient unless the user so specifies in an account setup of the user.